With this change, this script doesn't really release any artifacts anymore. Please provide more information in the PR description and update RELEASE-PROCESS.md to include this manual step and explain why one wouldn't want to normally execute it, which is the same reason why you are removing it from this file.

Since we are moving the release process to internal only, do we still need the release.sh and RELEASE-PROCESS.md in the OSS world? I'd propose just deleting them. When the time comes when we want to automate everything (tagging and publish release notes), we can refer to these files (they will be in Git history).

As long as the internal release process takes care of tagging, that's fine with me. We do need to document how to run the end-to-end test while this is an OSS project.

Currently tagging is not taken care of. To fully integrate with the internal build infra, we need something like #80.

Sync'ed with Javier offline. We will need two versions of release script, one for internal and one for external use case where ppl can build and host an image on their own. Please ignore the comment above. I've sent a PR internally for the internal release.sh script.

My understanding are the following statements:

• our team will publish tagged image with internal script.
• As it's an OSS project, we'd want to provide users instructions to:
  • build image,
  • run end-to-end test, and
  • push image to user owned image repository.

If the above statements are correctly, I will make the corresponding modification.

Yes, that makes sense to me.